Skip to content

Conversation

@jubrad
Copy link
Contributor

@jubrad jubrad commented Dec 2, 2025

Motivation

Tips for reviewer

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

- Moves the install, upgrade, and configuration docs into a subdirectory called Terraform Provider (Legacy)
- Creates aliases for each of the moved pages
- `Installation > Install on GCP `-> `Installation > Install on GCP > Terraform Provider (Legacy) > Install`
- Removed terraform references from the Deployment guideline appendix and pushed them into the Configuration appendix
- Changed from "Required configuration" to just "configuration"

docs: Relabel AWS guides as legacy Terraform guides

- Does the same work as the GCP commit

docs: Relabel Azure guides as legacy Terraform guides

- Does the same thing as the GCP commit
- Removes terraform configuation values given they weren't rendered. e.g. enable_disk_support

Update doc links

Add docs for new terraform modules.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant